Release 10.1A: OpenEdge Getting Started:
Progress OpenEdge Studio

Running the sample application

Running the SportsPro sample application gives you a feel for what you can build with the AppBuilder and SmartObject technology. The sample application contains several modules, each demonstrating a technique for solving a business problem. You will build parts of the Order Tracking System module in the tutorial and exercises later in this guide.

To run the SportsPro sample application:

If you have not already connected to the database, connect to your copy of the Sports2000 database. See "Creating and connecting to the Sports2000 database" section for information about connecting to your copy of the Sports2000 database.
Choose the AppBuilder icon from the Desktop toolbar to start the AppBuilder. One of the windows that appears by default is the PRO*Tools palette:



Choose the Run button from the PRO*Tools palette. The Run Procedure dialog box appears:



Type wmain.w for the Name of Procedure to Run.

If you copied the sample files as described in "Copying the sample files" section, you do not need to qualify the filename with its directory. The wmain.w file should be in your working directory which is a standard entry in your PROPATH.

Choose Run. The main window of the SportsPro sample application appears:



The SportsPro application’s main window is a SmartWindow. Most of the buttons on this SmartWindow use the FLAT–BUTTON attribute to create a two-dimensional look.

Table 2–2 lists the components used in the main window of the SportsPro sample application. It lists all the procedure files, all the SmartObjects, and any simple objects with important functions. Except for SmartObjects like SmartFilters for which the Application Development Model (ADM) supplies the masters, the procedure files and SmartObject master files listed in this table are in the gui folder in your working directory.

Table 2–2: Components of the SportsPro main window

Object or filename	Object type	Function
wmain.w	SmartWindow	Serves as a container for SDOs referenced by two of the modules and the buttons that launch the modules.
dcust	SmartDataObject (SDO)	Queries the Customer table to retrieve all customer records for the selected query. The query’s handle is passed into one of the modules.
BUTTON-1	Button	Launches wfndcust.w, passing it the handle for dcust.
BUTTON-2	Button	Launches wquery.w.
BUTTON-3	Button	Launches wdragdrop.w.
dorder	SDO	Queries the Order table to retrieve all order records for the selected query. The query’s handle is passed into one of the modules.
BUTTON-4	Button	Launches wfndord.w, passing it the handle for dorder.
BUTTON-5	Button	Launches wmntitem.w.
BUTTON-6	Button	Launches wordupd.w.
BUTTON-7	Button	Launches suppub.p.
BUTTON-8	Button	Launches gb2bintro.w. If you choose OK in the dialog box, it runs wstore.w.
BUTTON-9	Button	Launches worder.w.

Note: Table 2–2 and the tables in later sections present the objects and procedures from each module in an event-driven order. The objects contained in another object, and the procedures executed in that object, are listed directly after an object. Where data passes between objects and procedures, they are listed chronologically. Otherwise, objects are listed from top to bottom in their container.

Each of the buttons on the sample application’s main window launches a module. You can now examine these modules in turn. As you become more familiar with the OpenEdge products, you can return to these modules and examine them in greater detail. These modules show how to accomplish several common programming tasks.